Release 10.1A: OpenEdge Data Management:
DataServer for Microsoft SQL Server

DataServer for MS SQL Server logic

The flow chart in Figure 1–2 illustrates the DataServer’s internal logic.

Figure 1–2: DataServer logic

As shown in Figure 1–2, when you execute an application that accesses a MS SQL Server database, the Compiler translates Progress 4GL or SpeedScript statements into their SQL equivalents. The DataServer then issues the SQL statements to the ODBC driver through the ODBC API. The driver, which provides the software mechanisms for accessing and controlling the data source, processes the SQL statements, transfers them to the data source manager, and returns the results to OpenEdge through the ODBC API.

Note: The SQL presented in Figure 1–2 has been simplified for the purpose of focusing on the data flow.

To facilitate the flow of statements between client and server, the DataServer places OpenEdge equivalents for data definitions from a supported data source into a schema holder (a repository for data definitions for one or more MSS data sources). When the OpenEdge client or WebSpeed Agent executes statements and retrieves information from the data source, it relies on data definitions in the schema holder.